Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1588

reference: 295-tree-1
name: 1588
tree-preservation-order: undefined
295-tpo-1
uprn
address-text
point: POINT (-1.040935 50.897796)
geometry: MULTIPOLYGON (((-1.040864 50.897789,-1.040867 50.897803,-1.040877 50.897815,-1.040893 50.897825,-1.040912 50.897832,-1.040934 50.897834,-1.040956 50.897832,-1.040976 50.897826,-1.040992 50.897816,-1.041003 50.897804,-1.041006 50.897790,-1.041003 50.897776,-1.040993 50.897763,-1.040978 50.897753,-1.040958 50.897747,-1.040936 50.897744,-1.040914 50.897746,-1.040894 50.897752,-1.040878 50.897762,-1.040868 50.897775,-1.040864 50.897789)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL